Systems and methods for providing a covert password manager

ABSTRACT

The present invention relates to an application that is configured to provide secure access to confidential information. To protect the confidential information, the application may include functions that utilize a decoy application to disguise the functionality of the application. A unique sequence of inputs received through an interface associated with the decoy application may permit a user to access the confidential information. An authorized user that has been provided access to the confidential information may access configuration interfaces that permit the user to define the inputs that will serve as login credentials and to customize the appearance and functionality of the decoy application.

FIELD OF THE INVENTION

The present principles are directed to systems and methods forprotecting confidential information and, more particularly, to providinga password manager application that includes a covert login interfacefor accessing confidential information.

BACKGROUND OF THE INVENTION

Many computer applications are used to store confidential information.For example, an application may store confidential information such aspassword information, medical information, financial information orpersonal contact information. A user may be required to enter logincredentials before the user is permitted to access the confidentialinformation. For example, a user may be presented with a login screenthat includes an input form for receiving a username and password. Afterthe user has submitted the login credentials, the application maydetermine whether the login credentials are valid. If the logincredentials are determined to be valid, the user is given access to theconfidential information that is maintained by the application. On theother hand, the user may be denied access to the confidentialinformation if the login credentials are not valid.

Providing access to confidential information in the manner describedabove presents security concerns. The traditional login interfaceinvites unauthorized users to enter login credentials and to attempt toimproperly gain access to the confidential information that is protectedby the application. Hackers or other unauthorized users are aware thatthey are able to gain access to the confidential information if they areable to enter valid login credentials via the application's logininterface. Because the unauthorized users are aware of the location ofthe login interface, they can attempt to access the confidentialinformation by manually entering login credentials or by writingpassword cracking programs. While some applications incorporateadditional security features as part of the login process (e.g.,limiting the number of invalid login attempts that are permitted), thereis still a relatively high risk that unauthorized users may gain accessto underlying confidential information that is maintained by theapplication. Thus, there is a need to provide a means for accessingconfidential information that eliminates, or at least minimizes, theserisks.

SUMMARY OF THE INVENTION

The present invention relates to an application that is configured toprovide secure access to confidential information (e.g., passwordinformation, medical information, financial information, personalcontacts information or other type of confidential information). Toprotect the confidential information, the application may includefunctions that utilize a decoy application to disguise the functionalityof the application. A unique sequence of inputs received through aninterface associated with the decoy application may permit a user toaccess the confidential information. An authorized user that has beenprovided access to the confidential information may access configurationinterfaces that permit the user to define the inputs that will serve aslogin credentials and to customize the appearance and functionality ofthe decoy application.

In accordance with certain embodiments, a system, method and computerprogram product is provided that are configured to provide securedaccess to password information. An application may be provided thatincludes a password manager module and a decoy module. The passwordmanager module may be configured to perform password managementfunctions associated with accessing and managing password information. Adecoy module may be configured to disguise the password managementfunctions of the application by providing a decoy function and one ormore associated interfaces that are unrelated to managing the passwordinformation. In response to receiving a request from a user to accessthe application, instructions may be provided for rendering an interfaceassociated with the decoy function that includes an input form. Data maybe stored that associates an expected data type with at least one inputfield of the input form. Input received via the input form is evaluatedto determine whether or not the user is attempting to access thepassword information by comparing the data type of the input receivedvia the at least one input field with the expected data type that isassociated with the at least one input field. In response to determiningthat the data type of the input received via the at least one inputfield is not the expected data type, a determination is made that theuser is attempting to access the password information. The input is thenanalyzed to determine whether the user has submitted valid logincredentials. Access is provided to the password information in responseto determining that the user has submitted valid login credentials. Anauthorized user is provided access to a configuration interface thatallows the authorized user to specify the login credentials by selectingkeyboard events, click events and data form entry events and byassociating expected data types with input fields associated with thedata form entry events.

These and other features and advantages will become apparent from thefollowing detailed description of illustrative embodiments thereof,which is to be read in connection with the accompanying drawings.

BRIEF DESCRIPTION OF DRAWINGS

The inventive principles are illustrated in the figures of theaccompanying drawings which are meant to be exemplary and not limiting,in which like references are intended to refer to like or correspondingparts, and in which:

FIG. 1 is a block diagram of a system for securely protecting passwordinformation in accordance with certain embodiments of the presentinvention.

FIG. 2 illustrates an exemplary interface that includes a covert loginscreen in accordance with certain embodiments of the present invention.

FIG. 3 illustrates an exemplary interface for managing passwordinformation in accordance with certain embodiments of the presentinvention.

FIG. 4 illustrates an exemplary interface for configuring settings for acovert password manager in accordance with certain embodiments of thepresent invention.

FIG. 4A illustrates an exemplary interface for specifying logincredentials in accordance with certain embodiments of the presentinvention.

FIG. 5 is a flow chart of a method for validating login credentials inaccordance with certain embodiments of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In the following description, reference is made to the accompanyingdrawings that form a part hereof, and in which is shown by way ofillustration specific embodiments in which the invention may bepracticed. It is to be understood that other embodiments may be utilizedand structural changes may be made without departing from the scope ofthe present invention.

In accordance with certain embodiments, an application is configured toprovide secure access to confidential information. The confidentialinformation may include password information, medical information,financial information, personal contacts information or other type ofconfidential information. To protect the confidential information, theapplication may initially present a user with a “decoy application” thatis configured to display interfaces and perform functions that areunrelated to managing confidential information. The decoy applicationmay be a separate application that is launched by application thatmaintains the confidential information, or may represent a function thatis executed by the application. When a user executes or accesses theapplication, the features of the application relating to protecting andmanaging the confidential information are hidden and/or disguised.Inputs received from the user may be used to execute functionsassociated with the decoy application. One or more of the interfacesassociated with the decoy application may also serve as a covert loginscreen that enables the user to submit login credentials for accessingthe confidential information. The login screen is “covert” in the sensethat it appears to be an interface associated with executing thefunctionality of the decoy application and does not appear to be aninterface that will permit a user to submit login credentials foraccessing the confidential information. Input received via the interfacemay be used to execute decoy functions associated with the decoyapplication. However, entering input in a particular manner that ispredetermined by an authorized user will allow a user interacting withthe interface to access the confidential information. In certainembodiments, the input permits access to the confidential informationcomprises both one or more character-based inputs (e.g., text submittedvia an input form) and one or more non-character inputs (e.g., selectingor clicking-on an image that is displayed on an interface).

According to certain embodiments, the application may analyze the inputprovided by the user to determine whether the input is provided as anattempt to login and access the confidential information, or whether theinput is provided to execute the decoy application. This determinationmay be based, at least in part, on an expected data type for the input.For example, the interface that is displayed to the user may include aninput form or an input field that requests a numerical value, such as aninteger value or floating-point value, from the user. The applicationmay use the input to execute the decoy function in the event that datatype of the input is of the data type which is expected. On the otherhand, the application may determine that the user is attempting to loginand access the confidential information in the event that the inputprovided by the user is of an unexpected data type. For example, theapplication may determine that the user is attempting to login andaccess the confidential information if the user submitted a characterstring comprising alphabetical letters in an input field of a form inwhich an integer value was expected. Providing the unexpected data typemay cause the application to evaluate the input provided by the user asa login attempt. The input provided by the user may then be analyzed todetermine whether the input comprises valid login credentials foraccessing the confidential information.

The user may be presented with an interface for managing theconfidential information in the event that the user submitted validlogin credentials. In addition to providing interfaces that allow theuser to manage the confidential information, the user may also be givenaccess to one or more configuration interfaces that permit the user tocustomize certain features of the application. For example, theconfiguration interfaces may permit the user to define the sequence ofinput that comprises valid login credentials and to customize theappearance and functionality of the decoy application. On the otherhand, if the input provided by the user did not comprise valid logincredentials, the user may be denied access to the confidentialinformation and the input provided the user may be used to execute thedecoy function.

The embodiments described in this disclosure can be combined in variousways. Any aspect or feature that is described for one embodiment can beincorporated into any other embodiment mentioned in this disclosure.Moreover, any of the embodiments described herein may be hardware-based,software-based and preferably comprise a mixture of both hardware andsoftware elements. Thus, while the description herein may describecertain embodiments, features or components as being implemented insoftware or hardware, it should be recognized that any embodiment,feature or component that is described in the present application may beimplemented in hardware and/or software. In certain embodiments,particular aspects are implemented in software, which includes but isnot limited to firmware, resident software, microcode, etc.

Embodiments may include a computer program product accessible from acomputer-usable or computer-readable medium providing program code foruse by or in connection with a computer or any instruction executionsystem. A computer-usable or computer-readable medium may include anyapparatus that stores, communicates, propagates or transports theprogram for use by or in connection with the instruction executionsystem, apparatus, or device. The medium can be a magnetic, optical,electronic, electromagnetic, infrared, or semiconductor system (orapparatus or device) or a propagation medium. The medium may include acomputer-readable storage medium such as a semiconductor or solid statememory, magnetic tape, a removable computer diskette, a random accessmemory (RAM), a read-only memory (ROM), a rigid magnetic disk and anoptical disk, etc.

A data processing system suitable for storing and/or executing programcode may include at least one processor coupled directly or indirectlyto memory elements through a system bus. The memory elements can includelocal memory employed during actual execution of the program code, bulkstorage, and cache memories which provide temporary storage of at leastsome program code to reduce the number of times code is retrieved frombulk storage during execution. Input/output or I/O devices (includingbut not limited to keyboards, displays, pointing devices, etc.) may becoupled to the system either directly or through intervening I/Ocontrollers.

Network adapters may also be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems orremote printers or storage devices through intervening private or publicnetworks. Modems, cable modems and Ethernet cards are just a few of thecurrently available types of network adapters.

The discussion that follows describes an exemplary application that isconfigured to provide secure access to password information. However, itshould be recognized that the principles disclosed herein can be used toprovide access to any type of confidential information (e.g., financialinformation or medical information) and that appropriate modificationsmay be made to account for the type of confidential information that isbeing protected.

Referring now to the drawings in which like numerals represent the sameor similar elements and initially to FIG. 1, an exemplary system 100 isdisclosed for securely accessing password information. The system 100includes a covert password manager 150 that is configured to securelystore password information (and/or other confidential information) forauthorized users 105. An authorized user 105 may represent anyindividual that entitled to access the password information. The covertpassword manager 150 may represent an application that is stored onclient devices 110 that are operated by or associated with authorizedusers 105, or may represent an application that is stored or hosted onone or more servers 140 that are accessible to the over a network 190.

Unauthorized users 120 (e.g., hackers or other persons who do not havepermission to access the password information that is protected by thecovert password manager 150) may attempt to gain access to the passwordinformation stored by the covert password manager 150. For example, inthe case that the covert password manager 150 is installed on a clientdevice 110 associated with an authorized user 105, an unauthorized user120 may attempt to access the password information via the network 190(e.g., by remotely accessing the client device 110 using an authorizeduser device 130) or by physically utilizing the client device 110 (e.g.,if the client device 110 comes into the possession of the unauthorizeduser 120). Similarly, in the case that the covert password manager 150is installed on a server 140, an unauthorized user 120 may attempt toaccess the password information stored on the server 140 over thenetwork 190 utilizing an authorized user device 130. Regardless of wherethe covert password manager is installed, the covert password manager150 includes security features that can assist with preventingunauthorized users 120 from accessing the protected passwordinformation.

The network 190 illustrated in FIG. 1 may be any type of network, suchas one that includes the Internet, a local area network, a wide areanetwork, an intranet, etc. The client devices 110, unauthorized userdevices 130 and server 140 may be configured to communicate via wired orwireless links, or a combination of the two. In certain embodiments, theclient devices 110 and authorized user devices 130 may represent adesktop computer, laptop computer, cell phone, tablet device, personaldigital assistant or other type of computing device. Each of thesedevices 110 and 130 may be equipped with one or more computer storagedevices (e.g., RAM, ROM, PROM, SRAM, etc.) and one or more processingdevices (e.g., a central processing unit) that are capable of executingcomputer program instructions. The computer storage devices arepreferably physical, non-transitory mediums. The client devices 110 andauthorized user devices 130 may further include a display that iscapable of rendering interfaces and one or more input devices (e.g.,keyboard, microphone, camera, video camera, scanner, joystick, remotecontrol device, etc.). A user may manipulate interfaces rendered on thedisplay using the input devices to communicate and/or interact with acovert password manager 150 located on either the client device 110 orthe server 140.

The server 140 may also include one or more processors and one or morecomputer storage devices. The computer storage devices are preferablyphysical, non-transitory mediums. The server 140 may generally representany type of computing device that is capable of communicating with aclient device 110 and/or unauthorized user device 130 over the network190. In some embodiments, the server 140 comprises one or more mainframecomputing devices that execute a web server for communicating with thesedevices over the Internet.

The covert password manager 150 may be an application that stores,manages, secures and/or provides access to password information. Asmentioned above, the covert password manager 150 may be located on aclient device 110 or stored on a server 140. For example, the covertpassword manager 150 may represent a local password manager applicationthat is installed on and executed by a client device 110 that isassociated with an authorized user 105. Alternatively, or additionally,the covert password manager 150 may represent an application that isaccessed over a network 190 (e.g., by a client device 110 operated by anauthorized user 105). In the latter case, the covert password manager150 may be associated with a website or cloud-based service that stores,protects and provides access to the password information.

The password information that is protected and managed by the covertpassword manager 150 may represent any information or data that isassociated with authenticating a user, or which provides the user withaccess to an application or confidential information. For example, thepassword information which is protected by the covert password manager150 may include login information that permits a user to access awebsite, application or device. The password information may include,inter alia, data such as usernames, passwords, personal identificationnumbers, identification codes, security questions, e-mail addresses orany other type of similar information. The password information may bestored in a database associated with the covert password manager 150 andmay include one or more password entries each of which may be used tologin to one or more security portals. FIG. 3, which is discussed infurther detail below, illustrates an interface that displays exemplarypassword information that may be stored and associated with eachpassword entry (e.g., the name of the company or entity associated witha login portal, a uniform resource locator that identifies a web pagewhere the login credentials may be entered, a phone number, an address,etc.). Preferably, the database and associated password information isencrypted for security purposes.

In certain embodiments, the covert password manager 150 may include adecoy module 160 that provides functions associated with providing adecoy application. As used herein, the term “decoy application” does notnecessarily refer to an application or executable file that is separatefrom the covert password manager 150. Instead, in certain embodiments,the decoy application may represent functions that are performed by thecovert password manager 150. As explained herein, the decoy module 160may be configured to provide certain security features that are used toprotect the password information stored by the covert password manager150. In particular, the decoy module 160 may be configured to disguisethe covert password manager 150 such that it does not appear to be apassword manager application or other similar type of application. Forexample, in response to a user executing the covert password manager150, the decoy module 160 may present the user with one or moreinterfaces that serve to disguise the true functionality of the covertpassword manager 150 and which makes the covert password manager 150appear to be a credit card calculator application (e.g., as illustratedin FIG. 2), a gaming application (e.g., for a crossword puzzle or othertype of game), an educational application, a word processing applicationor other type of application. Generally speaking, the decoy module 160may disguise the covert password manager 150 to appear as any type ofdecoy application that is not associated with managing passwordinformation or other confidential information. In the case that thecovert password manager 150 is installed as a local application on aclient device 110, the decoy module 160 may include a function fordisguising an icon that is selectable to execute the application.

Preferably, the decoy module 160 is configured to provide functionalityassociated with the decoy application. For example, the decoy module 160may be configured to function as a credit card calculator in the casethat the decoy module 160 disguises the covert password manager 150 as acredit card calculator application. Thus, in response to receiving aninput from a user via an interface associated with the decoyapplication, the decoy module 160 may output financial information thatindicates how long it will take to pay off credit card debt. Similarly,the decoy module 160 may provide functionality that allows a user tocomplete a crossword puzzle game in the case that the covert passwordmanager 150 is disguised as a crossword puzzle application. Because thetrue functionality of the covert password manager 150 is disguised, anunauthorized user 120 that executes the covert password manager 150 maynever be aware that the underlying application is actually storing andprotecting password information (or other confidential information) and,thus, will be prevented from attempting to access the passwordinformation.

The password manager module 170 is configured to provide functionalityassociated with managing the hidden password information, e.g., such asstoring, encrypting, updating, editing and providing access to thepassword information. The password manager module 170 may providevarious interfaces to users for performing these functions. For example,FIG. 3, which is discussed in further detail below, discloses anexemplary interface 300 that may be presented to authorized users 105 bythe password manager module 170 for accessing or managing the passwordinformation after valid login credentials have been provided.

Before a user is permitted to access the password manager module 170and/or password information that is protected by the covert passwordmanager 150, the user may be required to provide certain input via oneor more of the interfaces that are provided as part of the decoyapplication that is presented to the user by the decoy module 160. Incertain embodiments, in response to receiving an input from a user, thecovert password manager 150 may evaluate the input and determine whetherthe received input was provided by an authorized user 105 or anunauthorized user 120. For example, a determination may be maderegarding whether the user is attempting to access the passwordinformation, or whether the received input was intended for use with thedecoy function associated with the application (e.g., whether the inputwas provided by a user who intended to utilize the decoy applicationbecause the user was unaware of underlying password managerfunctionality of the application). If it is determined that the inputwas intended to be utilized with the decoy application, the covertpassword manager 150 will utilize the input to execute the functionalityassociated with the decoy application. For example, in the case of adecoy credit card calculator application, the received input may be usedby the decoy application to calculate information related to paying offcredit card debt and the relevant credit card debt information may beoutput to the user. On the other hand, if it is determined that thereceived input was provided as part of an attempt to access the passwordmanager application, this will trigger the covert password manager 150to evaluate the input and determine whether the input comprises validlogin credentials for accessing the protected password information. Theuser may be provided with access to the password manager application ifthe user provides valid login credentials. Otherwise, the user will bedenied access. In the case that access is denied, the covert passwordmanager 150 preferably keeps the functionality of the password managermodule 170 disguised from the user and continues to present the decoyapplication and associated interfaces to the user.

Any input that is received while the decoy application is presented tothe user, or that is received via an interface associated with the decoyapplication, may be used as login credentials for accessing the passwordinformation that is protected by the covert password manager 170. Theinputs may include inputs received from any type of input deviceincluding, but not limited to, a keyboard device, a mouse device (e.g.,any left-clicks, right-clicks or inputs received from a scroll wheel onthe mouse device) and/or a touch screen device (e.g., any taps orgestures). In certain embodiments, the inputs may include inputs thatare received via an input form (e.g., which may include text fields,radio buttons, checkboxes or submit buttons) that is displayed as partof the decoy application. As explained below, a user may define theprecise sequence of inputs that will allow a user to access the passwordinformation.

In certain embodiments, the process of validating a user's login attemptinvolves evaluating the data type of an input provided via a form orinput field that is displayed to the user in connection with a decoyapplication. Commonly known data types may include integers, characterstrings, alphanumeric strings and floating-point numbers. An input field(e.g., such as a text field) on a form may appear to request a certaindata type and may be associated with the data type. For example, aninput field that requests a user's name would appear to be requesting adata type that is a character string, while an input field requesting adollar amount would appear to be requesting an input that is an integeror a floating-point data type. When a user provides an input via a formthat is provided as part of the decoy application, the covert passwordmanager 150 may evaluate the data type of the input that is provided viaone or more input fields and determine whether the provided input is ofa data type that would be expected for executing the decoy application.This may involve retrieving stored data that associates the data fieldswith particular data types. The input may be used to execute the decoyapplication in the case that the data type of the input is of a typethat is associated with the expected data type. On the other hand, areceived input that is not of an expected data type may notify thecovert password manager 150 that the user is attempting to login andaccess the password information. For example, if the user entered aninteger into a data field that requests a user's name, the covertpassword manager 150 may determine that the user is attempting to loginand access the password information.

In the case that it is determined that the user is attempting to loginand access the password information (e.g., because an unexpected datatype was received in an input field that was associated with aparticular data type), the covert password manager 150 may analyze anyinput provided by the user to determine whether the user has providedvalid login credentials. The input that is used to determine whether theuser has entered valid login credentials may be provided via the sameform which includes the input field that is used to determine whetherthe user is attempting to login and access the password information, ormay be provided via a separate form (e.g., possibly a form that ispresented on a separate interface associated with decoy application).Other inputs provided by the user which are submitted via the form mayalso be considered in determining whether the user has entered validlogin credentials.

In certain embodiments, all or part of the input that is used todetermine whether a user has entered valid login credentials comprisesone or more input events that are not entered via an input form.Commonly known input events that may be used as part of the validationprocess may include, for example, one or more click events received froma mouse device (e.g., associated with a left-click or right-clickprovided via a mouse), one or more gesture events received via a touchscreen device (e.g., tap gestures, swipe gestures, pan gestures or pressand hold gestures) or input events received from other types of inputdevices. For example, in certain embodiments, a user may be required toselect (e.g., with a mouse click or gesture) a portion of an interfacedisplayed as part of the decoy application in order to provide validlogin credentials. Thus, if the user did not select the portion of theinterface, the user would not be able to login and access the passwordinformation. Other types of inputs that may be used can include theselection of function keys (e.g., F1-F12 keys) or position or movementof a cursor.

In certain embodiments, the login credentials may comprise a combinationof both inputs received via a form and inputs that not received via aform (e.g., the user may be required to enter a password in a particulartext field provided via an input form and also to select a portion of aninterface that is not associated with the form in order to access thepassword information). Any combination of the above-described inputs maybe used to determine whether a user is attempting to login and accessthe password information and/or whether the user has entered valid logincredentials.

In certain embodiments, after an authorized user 105 has entered validlogin credentials, the password manager module 170 may permit theauthorized user 105 to access one or more configuration interfaces thatallow the user to configure a variety of different settings associatedwith the covert password manager 150. FIG. 4, which is discussed infurther detail below, illustrates an exemplary configuration interfacethat permits the settings associated with the covert password manager150 to be customized. The configuration interface may permit the user tospecify the login credentials that will permit the user to access thepassword information. For example, the user may specify which fields ofan input form that is provided as part of the decoy application are tobe used in determining whether the user has entered valid logincredentials. The user may also specify expected and/or unexpected datatypes for each of the input elements included in the form. Theconfiguration interface may also allow the user to specify other typesof inputs (e.g., click events or gesture events) that should be utilizedas part of the login credentials for accessing the password information.

In certain embodiments, the configuration interface may also permit auser to change the appearance and/or functionality of the decoyapplication. For example, the user may be permitted to adjust the title,text, name, icon, images and color scheme of the decoy application. Theuser may further be permitted to add, remove or edit input fields thatare included in the decoy application. In certain embodiments, the usermay be permitted to select different templates that allow the user toadjust the appearance and/or functionality of the application. Forexample, a set of design templates may be provided which permit the userto adjust the color scheme and/or interface layout of the decoyapplication. Likewise, a set of functional templates may be provided foradjusting the functionality of the decoy application. For example, afirst functional template may permit the user to configure the decoyapplication to be a credit card calculator application, while a secondfunctional template may permit the user to configure the decoyapplication to be a crossword puzzle application. Any number of designor functional templates may be provided. The user can select the designand functional templates in order to customize the decoy application.After the user has selected one or more templates, the user may accessinterfaces that permit the user to adjust default settings associatedwith the selected templates in order to further customize the decoyapplication. All of the information and data associated with customizingthe decoy application, including the templates and user selections, maybe stored in a database associated with the covert password manager 150.As explained below, other types of settings may also be customized usingthe configuration interface.

It should be recognized that the security features provided by thecovert password manager 150 provide several advantages that can be usedto assist a user with protecting password information or other types ofconfidential information. Even if an unauthorized user 120 gains accessto a device (e.g., personal computer, phone or server) that stores theinformation, the unauthorized user 120 would not be aware that there isan application that is storing the sensitive information since theapplication is disguised. Moreover, if the unauthorized user 120 issomehow aware of the existence of the underlying sensitive information,the unauthorized user 120 would have no idea how to access the passwordinformation since the covert password manager 150 does not present atraditional login screen or login process to authenticate a user. As aresult, the covert password manager 150 is able to provide a muchgreater level of security for the underlying information.

Other advantages stem from the customization features that are providedby the covert password manager 150. Because the configuration interfacesprovided by the covert password manager 150 permit the user to changethe appearance and/or functionality of the decoy application, the usercan design a unique decoy application that does not look like any otherdecoy application. If a user was not able to customize the decoyapplication in this manner, widespread distribution of the covertpassword manager 150 may become an issue since unauthorized users 105may eventually become aware of the appearance of the decoy application(since all would look the same) and may, therefore, recognize that theapplication is truly an application that protects sensitive information.

It should be noted that the system in FIG. 1 is merely meant todemonstrate an embodiment of an operating environment that can beutilized in conjunction with the inventive principles taught herein, andshould not be construed as limiting in any manner whatsoever. Theparticular configuration in FIG. 1 can be altered in numerous wayswithout departing from the principles herein. For example, it should benoted that the functionality of the server 140 in FIG. 1 may be carriedout by a plurality of servers. Likewise, although this figure depicts asingle client device 110 and two unauthorized user devices 130, anynumber of client devices 110 and unauthorized user devices 130 may beconnected to the system and the system may be configured in a variety ofdifferent ways (e.g., in a distributed computing environment,cloud-based environment, client-server environment, etc.). Furthermore,it should also be recognized that the functionality associated withcovert password manager 150 may be performed entirely by the clientdevices 110 or the server 140, or may be performed jointly by the clientdevices 110 and the server 140.

Moving on to FIGS. 2-4, exemplary interfaces are disclosed for providinga covert password manager 150. More specifically, FIG. 2 discloses anexemplary interface 200 that may be displayed by a decoy module 160 thatis configured to disguise the covert password manager 150 as a creditcard calculator application. FIG. 3 discloses an exemplary interface 300that may be displayed by the password manager module 170 for managingpassword information after valid login credentials have been provided.FIG. 4 illustrates an exemplary interface 400 for configuring settingsfor a covert password manager.

As shown in FIG. 2, the interface 200 includes an input form 250associated with a decoy credit card calculator application. Thisinterface may be disclosed in response to executing the covert passwordmanager 150 locally on a client device 110 or in response to accessing aserver 140 (e.g., via a web browser) that includes a covert passwordmanager 150. In the case that the covert password manager 150 islaunched locally on the client device 110, the application iconassociated with launching the covert password manager 150 may also bedisguised (e.g., may appear to be disguised as an icon associated with acredit card calculator application) to assist with disguising theapplication.

A user that is presented with the interface 200 may supply integerand/or floating-point values in the fields to utilize the credit cardapplication. The user may then select the “Calculate” button and thedecoy module 160 may utilize the input to perform calculations thatwould be expected of a normal or typical credit card calculatorapplication and to display the resulting calculations to the user. Inthis example, a user has provided input to the input form 250 thatindicates that the user's credit card balance is $8000, that theinterest rate for the credit card is 9.5% and that the user wishes topay off the debit with 48 months. In response to selecting the“Calculate” button, the decoy module 160 executes the software codeassociated with the decoy application to perform the relevantcalculations and also updates the interface to inform the user that theuser will be required to pay $200.99 per month to pay off the debtwithin the specified time frame.

The interface 200 also serves as a covert login screen that may beutilized to submit login credentials and access the password informationthat is protected by the covert password manager 150. In order todetermine whether the input provided via the form 250 is being submittedas an attempt to login and access the password information, one or moreof the input fields may be associated with an expected data type. Thecovert password manager 150 may analyze the data type of the informationsubmitted via the one or more of the fields. It may be determined thatthe user is attempting to login if the data type of the input providedvia the one or more of the input fields does not match the expected datatype that is associated with the one or more of the input fields.

In this example, it may be expected that the user will enter an integeror floating-point value in the upper input filed that requests theuser's credit card balance. Thus, if the user enters an integer orfloating-point value in this field, the decoy module 160 may utilizethis value to execute the decoy application. In this case, the covertpassword manager 150 may not evaluate the input any further for thepurpose of determining whether the user is attempting to login andaccess the password information. On the other hand, if the user enters atextual character string in this field, the covert password manager 150may analyze the input provided via the form 250 and attempt to use thisinformation to login and access the password information. Any inputprovided via the form 250 may be used to determine whether the user hasentered valid login credentials. For example, the character stringentered in the input field associated with the user's credit cardbalance may be used as a password that can be used to access thepassword information. Alternatively, while the submission of anunexpected data type in the credit card balance field may indicate thatthe user is attempting to access the password information, the inputprovided via this field or other input fields of the form 250 may beused as a username and/or password for accessing the passwordinformation.

In certain embodiments, other types of input and/or input events may beused in conjunction with the input provided via the form 250 todetermine whether the user may access the password information. Forexample, as part of the login process, the user may be required to clickon the image of the calculator located on the right-hand portion of theinterface. In other cases, the user may be required to press and hold aparticular combination of keys (e.g., the shift key and escape key) fora predetermined period of time before submitting the input via the inputform 250. Other types of inputs may also be utilized as part of thelogin process.

FIG. 3 is an exemplary interface 300 that may be displayed by thepassword manager module 170 to a user who has entered valid logincredentials. As shown, the user may be presented with a listing ofpassword entries 310. Each entry in the listing 310 may be associatedwith password information for accessing a particular authentication orlogin portal. For example, the password information for one entry may beused to login to a Facebook™ account, while the password informationassociated with another entry may be used to login to a user's Google™account. For each entry, the listing 310 displays the name of account, ausername, a password and an answer to a security question.

An entry in the listing may be selected to view and/or edit detailspertaining to the password information for the entry and/or detailsassociated with the particular account that is associated with theentry. Any data associated with an entry may be displayed in thedetailed information window 320 located on the right-hand portion of theinterface 300. In this example, the detailed information window 320includes the following information for the selected entry: the name ofthe account, the account number, a uniform resource locator (URL)associated with the account, a username, a password, a personalidentification number (PIN), a security question, a contact, phonenumber, an e-mail address, a street address, additional notes associatedwith the account (e.g., which may include a description regarding whatthe password information is being used to access), and an accountbalance. The password manager module 170 may generally store anyinformation that is associated with accessing or logging into anaccount, or other information that is otherwise associated with theaccount.

FIG. 4 illustrates an exemplary configuration interface 400 that may beused to customize the settings of the covert password manager 150. Adatabase selection option 410 permits the user to select the databasethat should be configured. For example, the covert password manager 150may permit the user to create a plurality of different databases forsecurely storing password information (or other confidentialinformation) and may allow the user to store the databases anywhere(e.g., on a local device, on a local network or at a location on theInternet). Different configuration settings can be specified for eachdatabase that is created. Thus, the database selection option 410permits the user to select that database for which the settings are tobe configured.

An inactivity option 430 permits the user to specify a time limit afterwhich the user will be logged out of the password management portion ofthe application. For example, after a user has entered valid logincredentials and logged into the password management module, the user mayautomatically be logged out or locked out if the user is inactive for apredetermined time period (e.g., five minutes) which can be specified bythe inactivity option 430.

A password field 420 permits the user to specify a password that shouldbe used as part of the login credentials and a credential entry option450 permits the user to specify the parameters for entering the logincredentials. In certain embodiments, the credential entry option 450 mayinclude a variety of different pre-configured options for entering thelogin credentials. In this example, an option is selected that specifiesthat the password specified by the password field 420 should be enteredin the amount per month field (i.e., the third input field from the topas shown in FIG. 2) and that the user should select the text located tothe left of the balance field (i.e., the text which recites “Enter yourcredit card balance:”) as part of the process of submitting logincredentials.

The credential entry option 450 may provide numerous additional optionsfor submitting login credentials as well. As another example, an optionmay be provided that specifies that the user is to enter the password ina particular input field and subsequently select the F12 (or otherfunction key) in order to login. As an even further example, thecredential entry option 450 may provide an option that specifies thatthe specified password should be entered into a particular input fieldand that the image of the calculator (located on the right portion ofFIG. 2) should be selected (e.g., with a mouse click or tap gesture) inorder to login. Other login options may also be provided by thecredential entry option 450. All of the predetermined settingsassociated with the credential entry option 450 may be stored in adatabase associated with the covert password manager 150. In certainembodiments, the user may be permitted to add additional login optionsand/or edit existing login options that can be used for specifying thelogin credentials (e.g., as discussed below with reference to FIG. 4A).

Another option 460 permits a user to specify whether a single credentialentry option 450 should be used to specify the login credentials, orwhether a plurality of credential entry options 450 should be utilizedto specify the login credentials. For example, as illustrated in FIG.4A, login credentials may be specified which require a plurality ofdifferent actions to be taken.

As mentioned above, the process of evaluating whether a user has enteredvalid login credentials may also involve analyzing whether the user hasprovided an expected or unexpected data type in one or more of thefields provided via a form associated with the decoy application. Thus,the configuration interface 400 may also include a data type detectionoption 440 that permits the user to specify which input fields should beanalyzed for this purpose. In this example, the data type detectionoption 440 includes two preferences. A first preference specifies thatentry of an unexpected data type in any input field (e.g., any field inFIG. 2) indicates that a user is attempting to login. Thus, if the userentered an unexpected data type in any of the input fields, the covertpassword manager 150 may determine that the user is attempting to loginand would evaluate the input provided by the user to determine whetherthe user entered valid login credentials (e.g., may evaluate the inputbased on the settings specified by the password field 420 and thecredential entry option 450).

The second preference specifies that the entry of the unexpected datatype in only certain fields will be interpreted as a login attempt. Incertain embodiments, the selected field may be a field that isidentified by the credential entry option 450. In certain embodiments,the user may be permitted to select any field included in a formprovided by the decoy application and the data type of the inputreceived via the field may be evaluated for the purpose of determiningwhether the user is attempting to login and access the passwordinformation.

An allowable error option 470 allows the user to specify the permissiblenumber of login attempts that are allowed before a user is no longerpermitted to login and access the password information (at least for alimited period of time). A first security option 480 allows the user tospecify certain actions that can be taken in response to receivinginvalid login credentials. In this example, the user selected an optionthat specifies that the password information protected by the covertpassword manager 150 should be deleted in response to receiving fiveconsecutive invalid login attempts. Rather than deleting the passwordinformation, other exemplary settings may be selected. For example, theuser may select an option that causes the covert manager application 150to disable the login feature or to send an alert (e.g., via e-mail ortext message) to the user in response to receiving a certain number ofinvalid login attempts. In certain embodiments, the user may alsospecify the number of invalid login attempts that will trigger theaction identified by the first security option 480.

A second security option 490 may allow the user to specify a passwordthat should be used to re-access the password information after the userhas been logged out or locked out due to inactivity. For example, asexplained above, an inactivity option 430 may lock a user out if theuser is inactive for a predetermined period of time. Thus, the secondsecurity option 490 permits the user to specify a password that willpermit the user to access the password information after being loggedout/locked out.

FIG. 4A illustrates an exemplary interface 400A that permits a user tospecify and define login credentials for accessing the passwordinformation that is protected by the covert password manager 150. Inthis example, the user is permitted to select up to three actions thatmay be required for submitting valid login credentials. Exemplaryactions may include the following:

-   -   Key press events: If an action for a key press event is        selected, then the user may further select a function key (or        other key) on a keyboard that is to be associated with the key        press event. A a user who is attempting to login and access the        password information may then be required to select the        specified key as part of the input that is required to login and        access the password information.    -   Data form entry events: A data form entry event generally        relates to an input event that is received via an input form. If        an action for a data form entry event is selected, a user        attempting to login and access the password information may be        required to enter data having a particular data type into an        input field of a form provided in conjunction with the decoy        application. Notice in the exemplary interface shown in FIG. 4A,        the drop-down menu permits a user to select and specify the        input field (e.g., “Edit Box One” and “Edit Box Three”), as well        as the data type that is associated with the field (e.g.,        “UInt32” or “Double”).    -   Click events: If an action for a click event is selected, then a        user attempting to login and access the password information may        be required to perform a mouse click (e.g., a left-click or        right-click) on a portion of an interface that is provided in        conjunction with the decoy application. For example, a user may        be required to click on an image or text (e.g., a text label for        an input field or image caption). The user may specify the        portion of the interface that is to be clicked on or selected.

After the user has selected one or more actions and associatedparameters for defining the login credentials, the user may select abutton for saving the new settings as a new login option and/or changingthe existing login settings for the covert password manager 150. Theuser may also select an option for displaying an exemplary login screenthat is configured to utilize the new login settings. This enables theuser to test the login settings that have been created before thesettings are actually applied to the covert password manager 150.

FIG. 5 is a flow chart of a method 500 for validating login credentialsin accordance with certain embodiments of the present invention. Thisexemplary method may be executed by a server 140 or a user device (e.g.,an authorized user device 110). A covert login interface is displayed inresponse to a user accessing a password manager application (step 510).FIG. 2 illustrates an exemplary covert login interface that disguisesthe password manager application to look like a credit card calculatorapplication.

Next, input is received from the user via the covert login interface(step 520). As explained above, the input may be received via a formthat is presented on the covert login interface and/or may include othertypes of inputs (e.g., click inputs, gesture inputs or inputs fromfunction keys). The input provided by the user is evaluated in order todetermine whether the input matches an expected data type (step 530).For example, an input field included on a form that is displayed on thecovert login interface may be associated with an expected data type. Theexpected data type may represent a data type that would be expected if auser was attempting to execute the decoy application associated with thecovert login interface. For example, in the exemplary interface shown inFIG. 2, the expected data type may include integer or floating pointvalues, since the covert login interface would appear to be requestingnumerical values for computing the credit card payment information.

A determination is then made as to whether the data type of the receivedinput matches the expected data type (step 540). If the data type of theinput does match the expected data type, then it may be assumed that theuser is not an authorized user and the input may be utilized to executea decoy function (e.g., to execute a function for performing credit cardpayment calculations) (step 550).

On the other hand, if the data type of the received input does not matchthe expected data type, then the input provided by the user may beanalyzed to determine whether the user has submitted valid logincredentials (step 560). The input will once again be utilized to executethe decoy function in the case that it is determined that valid logincredentials have not been provided. Otherwise, if valid logincredentials have been provided, then the user is granted access to thepassword information (step 570). For example, the user may be presentedwith the interface shown in FIG. 3 which permits the user to access andmanage the password information.

While there have shown and described and pointed out various novelfeatures of the invention as applied to particular embodiments thereof,it will be understood that various omissions and substitutions andchanges in the form and details of the systems and methods described andillustrated may be made by those skilled in the art without departingfrom the spirit of the invention. Amongst other things, the steps shownin the methods may be carried out in different orders, in many caseswhere such may be appropriate. Those skilled in the art will recognize,based on the above disclosure and an understanding therefrom of theteachings of the invention, that the particular hardware and devicesthat are part of the system described herein, and the generalfunctionality provided by and incorporated therein, may vary indifferent embodiments of the invention. Accordingly, the particularsystem components shown in the figures are for illustrative purposes tofacilitate a full and complete understanding and appreciation of thevarious aspects and functionality of particular embodiments of theinvention as realized in system and method embodiments thereof. Thoseskilled in the art will appreciate that the invention can be practicedin other than the described embodiments, which are presented forpurposes of illustration and not limitation.

What is claimed is:
 1. A system configured to provide secured access topassword information, comprising: a computing device having a processorand physical memory, the physical memory storing instructions that causethe processor to: provide an application that is configured to protectpassword information, wherein the application comprises: a passwordmanager module configured to perform password management functionsassociated with accessing and managing password information; and a decoymodule configured to disguise the password management functions of theapplication by providing a decoy function and one or more associatedinterfaces that are unrelated to managing the password information; inresponse to receiving a request from a user to access the application,provide instructions for rendering an interface associated with thedecoy function that includes an input form; store data that associatesan expected data type with at least one input field of the input form;evaluate input received via the input form to determine whether or notthe user is attempting to access the password information by comparingthe data type of the input received via the at least one input fieldwith the expected data type that is associated with the at least oneinput field; determine that the user is attempting to access thepassword information in response to determining that the data type ofthe input received via the at least one input field is not the expecteddata type; analyze the input to determine whether the user has submittedvalid login credentials; and provide access to the password informationin response to determining that the user has submitted valid logincredentials; wherein the application permits an authorized user toaccess a configuration interface that allows the authorized user tospecify the login credentials by selecting keyboard events, click eventsand data form entry events, and by associating expected data types withinput fields associated with the data form entry events.
 2. The systemof claim 1, wherein the input is utilized to execute the decoy functionin response to determining that the data type of the input received viathe at least one input field matches the expected data type associatedwith the at least one input field.
 3. The system of claim 1, wherein thelogin credentials are comprised of one or more character-based inputsthat are submitted via the input form and one or more non-characterinputs, and the one or more non-character inputs are selected from thegroup consisting of: a click input on an interface element that is notpart of the input form, a position of a cursor on an interfaceassociated with the decoy function, or a selection of a function keywhile an interface associated with the decoy function is displayed. 4.The system of claim 1, wherein the user is provided access to theconfiguration interface after the user has provided valid logincredentials and is given access to the password information.
 5. Thesystem of claim 4, wherein the configuration interface permits the userto specify the login credentials and the configuration interface atleast includes: a first input option that enables a keyboard eventpertaining to a function key to be associated with the logincredentials; a second input option that enables a click event to beassociated with the login credentials; and a third input option thatenables a data form entry event to be associated with the logincredentials; wherein selections associated with the first input option,second input option and third input option are stored in a databaseassociated with the application and the selections are retrieved fromthe database to determine whether the user has entered valid logincredentials.
 6. The system of claim 4, wherein the configurationinterface permits the user to customize the design, appearance andfunctionality of the interfaces associated with the decoy module.
 7. Thesystem of claim 6, wherein the user is provided with a plurality ofdesign templates for customizing the design and appearance of theinterfaces and a plurality of functional templates for selectingdifferent decoy functions.
 8. A method for providing secured access topassword information, comprising: providing an application that isconfigured to protect password information, wherein the applicationcomprises: a password manager module configured to perform passwordmanagement functions associated with accessing and managing passwordinformation; and a decoy module configured to disguise the passwordmanagement functions of the application by providing a decoy functionand one or more associated interfaces that are unrelated to managing thepassword information; in response to receiving a request from a user toaccess the application, providing instructions for rendering aninterface associated with the decoy function that includes an inputform; storing data on a non-transitory computer storage medium thatassociates an expected data type with at least one input field of theinput form; evaluating, with a processor, input received via the inputform to determine whether or not the user is attempting to access thepassword information by comparing the data type of the input receivedvia the at least one input field with the expected data type that isassociated with the at least one input field; determining that the useris attempting to access the password information in response todetermining that the data type of the input received via the at leastone input field is not the expected data type; analyzing, with aprocessor, the input to determine whether the user has submitted validlogin credentials; and providing access to the password information inresponse to determining that the user has submitted valid logincredentials; wherein the application permits an authorized user toaccess a configuration interface that allows the authorized user tospecify the login credentials by selecting keyboard events, click eventsand data form entry events, and by associating expected data types withinput fields associated with the data form entry events.
 9. The methodof claim 8, wherein the input is utilized to execute the decoy functionin response to determining that the data type of the input received viathe at least one input field matches the expected data type associatedwith the at least one input field.
 10. The method of claim 8, whereinthe login credentials are comprised of one or more character-basedinputs that are submitted via the input form and one or morenon-character inputs, and the one or more non-character inputs areselected from the group consisting of: a click input on an interfaceelement that is not part of the input form, a position of a cursor on aninterface associated with the decoy function, or a selection of afunction key while an interface associated with the decoy function isdisplayed.
 11. The method of claim 8, wherein the user is providedaccess to the configuration interface after the user has provided validlogin credentials and is given access to the password information. 12.The method of claim 11, wherein the configuration interface permits theuser to specify the login credentials and the configuration interface atleast includes: a first input option that enables a keyboard eventpertaining to a function key to be associated with the logincredentials; a second input option that enables a click event to beassociated with the login credentials; and a third input option thatenables a data form entry event to be associated with the logincredentials and which permits a data type to be associated with the dataform entry event; wherein selections associated with the first inputoption, second input option and third input option are stored in adatabase associated with the application and the selections areretrieved from the database to determine whether the user has enteredvalid login credentials.
 13. The method of claim 11, wherein theconfiguration interface permits the user to customize the design,appearance and functionality of the interfaces associated with the decoymodule.
 14. The method of claim 13, wherein the user is provided with aplurality of design templates for customizing the design and appearanceof the interfaces and a plurality of functional templates for selectingdifferent decoy functions.